Skip to content

Conversation

@missirol
Copy link
Contributor

PR description:

  • Development of HLT menus for CMSSW_12_4_X.
  • Migration of HLT configs to release template CMSSW_12_4_0.
  • Introduction of V1.2 frozen (GRun) menu to be used for MC production in 12_4_X.

This is the PR for the master branch, which will then be backported to 12_4_X (the latter is the release cycle currently used for HLT-menu development for Run 3).

Includes the integration of the following JIRA tickets.

  • CMSHLT-2267: [EXO] Update of displaced-ditau trigger
  • CMSHLT-2287: [TSG] Update of HLTDebug* EventContents with DQMGPUvsCPU output collections
  • CMSHLT-2304: [MUO,BPH] Change L1T seed of HLT_Mu15, remove HLT_Mu7p5_TkX
  • CMSHLT-2315: [ECAL] Disable energy-recovery in ECAL RecHit producers
  • CMSHLT-2326: [EXO] Update of 2 triggers with new displaced-global-muon reconstruction
  • CMSHLT-2336: [TSG] Disable unclaimed triggers (90 triggers in total)
  • CMSHLT-2343: [TSG] Add DQMGPUvsCPU stream to HIon and PRef menus
  • CMSHLT-2344: [BPH] Disabled HLT_DoubleMu2_Jpsi_DoubleTkMu0_Phi_v
  • CMSHLT-2346: [BPH] Removed *ToCSCS* single-muon 2018-Parking triggers and dataset
  • CMSHLT-2348: [BPH] Disabled single-muon 2018-Parking triggers (integrated partially; Paths not yet removed nor replaced)
  • CMSHLT-2353: [L1T] Update of MET L1T seeds

In addition, HLT configs will now use cms.ConditionalTasks instead of cms.Tasks thanks a recent update of ConfDB (V03-04-00). Further details on the reasons behind this change can be found in #36938.

PR validation:

TSG tests.

If this PR is a backport, please specify the original PR and why you need to backport that PR:

N/A

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38482/30703

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @missirol (Marino Missiroli) for master.

It involves the following packages:

  • Configuration/HLT (hlt)
  • Configuration/PyReleaseValidation (pdmv, upgrade)
  • HLTrigger/Configuration (hlt)

@Martin-Grunewald, @jordan-martins, @AdrianoDee, @bbilin, @cmsbuild, @missirol, @srimanob, @kskovpen can you please review it and eventually sign? Thanks.
@makortel, @kpedro88, @fabiocos, @Martin-Grunewald, @silviodonato, @trtomei, @beaucero, @slomeo this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@missirol
Copy link
Contributor Author

enable gpu

@missirol
Copy link
Contributor Author

please test

@missirol missirol changed the title HLT menu development for CMSSW_12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X] HLT menu development for 12_4_X (4/N) + migration to 12_4_0 + frozen menu V1.2 for 2022 [12_5_X] Jun 23, 2022
@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-865996/25736/summary.html
COMMIT: 7d1b9f3
CMSSW: CMSSW_12_5_X_2022-06-23-1100/el8_amd64_gcc10
Additional Tests: GPU
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/38482/25736/install.sh to create a dev area with all the needed externals and cmssw changes.

GPU Comparison Summary

Summary:

  • No significant changes to the logs found
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 0 differences found in the comparisons
  • Reco comparison had 1 failed jobs
  • DQMHistoTests: Total files compared: 4
  • DQMHistoTests: Total histograms compared: 19864
  • DQMHistoTests: Total failures: 9
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 19855
  • DQMHistoTests: Total skipped: 0
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 3 files compared)
  • Checked 12 log files, 9 edm output root files, 4 DQM output files
  • TriggerResults: found differences in 3 / 3 workflows

Comparison Summary

Summary:

  • No significant changes to the logs found
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3654169
  • DQMHistoTests: Total failures: 1847
  • DQMHistoTests: Total nulls: 10
  • DQMHistoTests: Total successes: 3652290
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -10252.140000000001 KiB( 49 files compared)
  • DQMHistoSizes: changed ( 11634.0,... ): -1706.259 KiB HLT/BPH
  • DQMHistoSizes: changed ( 11634.0,... ): -2.432 KiB HLT/Filters
  • Checked 208 log files, 45 edm output root files, 50 DQM output files
  • TriggerResults: found differences in 4 / 49 workflows

@missirol
Copy link
Contributor Author

missirol commented Jun 24, 2022

@Martin-Grunewald

I noticed that runIntegration.csh does not make use of the Frozen GRun menu. Should that be updated similarly to runOne.csh ? If so, should I update this in this PR (and backport), or in a future one?

@Martin-Grunewald
Copy link
Contributor

Yes, it should be added under 'frozen' together with the Fake* in these PRs.

@Martin-Grunewald
Copy link
Contributor

... and also under 'all'

@missirol
Copy link
Contributor Author

under 'frozen' together with the Fake*

In runOne, "frozen" does not include the Fake menus (those are only under "fake"). I assume we want to keep the same structure ("frozen"=frozenGRun, "fake"=fake menus).

@Martin-Grunewald
Copy link
Contributor

Ah yes, fake for the fakes, frozen for the real non-fake menus such as 2022v12!!

@missirol missirol force-pushed the HLTdevelopment124X_for125X branch from 7d1b9f3 to 443361e Compare June 24, 2022 07:36
@missirol
Copy link
Contributor Author

missirol commented Jun 24, 2022

+hlt

@missirol
Copy link
Contributor Author

@cms-sw/pdmv-l2 @cms-sw/upgrade-l2 , please consider reviewing this PR and its backport. The latter is needed for the upcoming MC production in 12_4_X.

The changes in Configuration/PyReleaseValidation are simple.

@missirol
Copy link
Contributor Author

missirol commented Jun 24, 2022

I think I understand now the differences in GlobalRecHitsV/HCals.

This PR modifies the FEVTDEBUGHLT EventContent adding (among others) new collections of HCAL RecHits, i.e. hltHbherecoLegacy and hltHbherecoFromGPU (the latter is filled only on GPU).

In the wfs in question, this modifies the output of "step2", which is the input to "step3". The histograms in questions are filled in "step3" by the Validation plugin GlobalRecHitsAnalyzer. For HCAL RecHits only, the latter plugin uses all the HcalRecHit collections available in the input file (in the input file + in the current job, i.e. step3):

consumesMany<edm::SortedCollection<HBHERecHit, edm::StrictWeakOrdering<HBHERecHit>>>();

This can explain the differences (more entries in those HCAL plots post-PR, because the EDM input contains more collections of HCAL RecHits). I dare say that HLT makes no guarantee that the collections in FEVTDEBUHLT are mutually exclusive, so the logic of the Validation plugin might have to improved (by the relevant experts).

@srimanob
Copy link
Contributor

+Upgrade

From the upgrade side, only HLT key is updated from 2021 to 2022.

@perrotta
Copy link
Contributor

urgent

@missirol
Copy link
Contributor Author

@cms-sw/pdmv-l2 , a second ping to review this PR (and its backport). The only change to review is the renaming of HLT:@relval2021 to HLT:@relval2022.

We should start testing these PRs in IBs asap, to exclude unexpected issues in time for the next 12_4_X release early next week.

@kskovpen
Copy link
Contributor

+pdmv

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@missirol
Copy link
Contributor Author

Thanks, @kskovpen . Could you please sign the backport (#38483) as well?

@kskovpen
Copy link
Contributor

kskovpen commented Jun 25, 2022

Sorry - just did!

@qliphy
Copy link
Contributor

qliphy commented Jun 25, 2022

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants